Profile and consent accrual

ABSTRACT

Consent management between a client and a network server. In response to a request for consent, a central server determines if requested user information is included in a user profile associated with a user and if the user has granted consent to share the requested user information. A user interface is provided to the user via a browser of the client to collect the requested user information that is not included in the user profile and the consent to share the requested user information from the user. After receiving the user information provided by the user via the user interface, the service provided by the network server is allowed access to the received user information, and the central server updates the user profile. Other aspects of the invention are directed to computer-readable media for use with profile and consent accrual.

TECHNICAL FIELD

Embodiments of the present invention relate to the field of computernetwork environments. In particular, embodiments of this inventionrelate to easily accruing user information used by related applicationsor sites that are affiliated with a multi-site user authenticationsystem.

BACKGROUND OF THE INVENTION

Web sites, or Internet sites, often provide information, products,services, and the like to their users. Many web sites desire users to“register” before their web servers will grant access to the users.During registration, a user typically supplies personal information suchas username, account number, address, telephone number, e-mail address,computer platform, age, gender, and/or hobbies to the registering website. The registration information may be necessary to completetransactions (e.g., commercial or financial transactions). Typically,the information also permits the web site to contact the user directly(e.g., via electronic mail) to announce, for example, specialpromotions, new products, or new web site features. Additionally, websites often collect user information so web site operators can bettertarget future marketing activities or adjust the content provided by thesites.

When registering a user for the first time, a web site may request thatthe user select a login identifier, or login ID, and an associatedpassword. The login ID allows the web site to identify the user andretrieve information about the user during subsequent user visits to theweb site. Generally, the login ID is unique to the web site such that notwo users have the same login ID. The combination of the login ID andpassword associated with the login ID allows the web site toauthenticate the user during subsequent visits to the web site. Thepassword also prevents others (who do not know the password) fromaccessing the web site using the user's login ID. This passwordprotection is particularly important if the web site stores private orconfidential information about the user, such as financial informationor medical records.

Using a presently available multi-site user authentication system, a webuser can maintain a single login ID (and associated password) foraccessing multiple, affiliated web servers or services. Such a systempermits the user to establish a unique account identified by, forexample, an e-mail address.

Large Internet service providers often have many different web sitesthrough which they offer services to consumers. Moreover, a single webservice can actually be made up of many different content providers.Other sites may be used to provide content related to children'sinterests, e-shopping, news, and so forth. Consumers usually perceivethese related sites as being essentially the same service. Further, asInternet usage migrates to a subscription-based model that includescontent and services from a variety of different sites, the need existsfor accurately sharing common information (e.g., billing andsubscription information) between related sites.

As described above, a web site often gathers personal information aboutits users for later use. A typical privacy statement for a web sitedescribes how the site protects and uses personal information. Thepolicy will likely specify first what information the site collects. Forexample, the site may maintain a profile for the user includinginformation (attributes) such as the user's e-mail address, first andlast name, country or region, state or territory, ZIP code or postalcode, language preference, time zone, gender, birth date, occupation,telephone number(s), credit card information, billing and shippingaddresses, password, PIN, secret question and secret answer, clothingsizes, music preferences, and the like. Inasmuch as this profileinformation can be quite sensitive, the typical policy also specifieshow the information will or will not be used. For example, a web site'sprivacy policy may forbid the site from selling or renting a user'spersonal information without prior consent. The same policy, however,may detail a number of permitted uses (e.g., resolving customer supportinquiries, performing statistical analyses of the site's services,conforming to legal requirements, protecting the personal safety ofusers or the public). A typical policy often specifies certaincircumstances under which disclosures or uses of information arepermitted and those other circumstances under which they are not.

Users typically do not like to provide too much information during afirst time sign-up or registration. If asked to provide more informationthan needed for sign-up or registration, the users may provideinaccurate information in order to speed up the registration process.Such inaccurate user information undermines the purpose of having aprofile store.

Furthermore, there has been an increasing movement in local, federal,and international governments to require web sites to provide consumersexplicit notice and choice in order for the consumers to grantaffirmative consent for the sites to use the obtained consumerinformation. Prior systems and methods do not effectively address suchconsent requirements.

Another disadvantage of the prior systems and methods is that there isno mechanism for web sites to collect the same information from users.In other words, web sites get differing amounts of information dependingon which users access the web sites. As a result, web sites are forcedto collect the missing user information manually or to limit the servicefeatures for users who have not provided the necessary information.

Accordingly, a solution is needed that allows accruing consent for anaffiliated site or service to use obtained user information whilecomplying with the various consent requirements.

SUMMARY OF THE INVENTION

Embodiments of the invention overcome one or more deficiencies in theprior art by providing, among other things, improved sharing ofinformation among related sites. Information accrual may be deferred tothe time when the users see the relevance of information collectionaccording to embodiments of the invention. For example, a user is morelikely to provide accurate information regarding a style of car desiredwhen visiting a car-buying site than if asked for the same informationduring initial registration of an unrelated site. A user profileaccording to one embodiment of the invention effectively storesuser-specific information that identifies a user with respect to one ormore sites or services. When the user visits a particular site/service,the site/service may desire some information regarding the user. Oneembodiment of the present invention effectively determines if thedesired information is stored in the user profile. If the desiredinformation is not stored in the user profile, embodiments of theinvention advantageously provide a user interface (UI) to accrue thedesired information from the user. If the user grants consent for thesite/service to use the accrued information, embodiments of theinvention effectively provide the accrued information to thesite/service. Embodiments of the invention also advantageously provideintention information, retention information, and privacy policyassociated with a particular site/service for the user to decide whetherto grant consent to share the desired information with the site/service.Moreover, the features of embodiments of the present invention describedherein are less laborious and easier to implement than currentlyavailable techniques as well as being economically feasible andcommercially practical.

Briefly described, a method employing aspects of the invention managesconsent between a client and a network server. The client and thenetwork server are coupled to a data communication network. The networkserver provides a service to a user via the client. And the clientoperates a browser configured to permit the user to communicate on thedata communication network. The method includes maintaining a userprofile associated with the user. The method also includes receiving arequest from the service provided by the network server for userinformation associated with the user and for consent to use therequested user information. In response to the request for consent, themethod includes determining if the requested user information isincluded in the user profile. The method also includes providing a userinterface via the browser to collect the requested user information thatis not included in the user profile from the user. The method furtherincludes receiving the user information provided by the user via theuser interface. The method further includes allowing access by theservice to the received user information.

In another embodiment of the invention, an authentication systememploying aspects of the invention includes an authentication servercoupled to a data communication network. The authentication system alsoincludes an authentication database associated with the authenticationserver. The authentication database is configured to storeauthentication information for comparison to login information providedby a user for authenticating the user. The authentication database isfurther configured to store user-specific information identifying theuser with respect to one or more services provided by at least oneaffiliate server coupled to the data communication network. And theaffiliate server is configured to provide the one or more services tothe user via a client coupled to the data communication network. Theauthentication server is configured to receive a request from the userfor a service to be provided by the affiliate server. The authenticationserver is further configured to authenticate the user responsive to therequest when login information retrieved from the user via the datacommunication network matches the authentication information stored inthe authentication database. And the authentication server is furtherconfigured to maintain a user profile storing the user-specificinformation, to receive a request from the requested service for userinformation associated with the user and consent to use the requesteduser information, to determine, in response to the request for consent,if the requested user information is stored in the user profile. Theauthentication server is configured to provide a user interface tocollect the requested user information that is not stored in the userprofile from the user, to receive the user information provided by theuser via the user interface in response, and to allow access by therequested service to the received user information.

In yet another embodiment of the invention, computer-readable mediaemploying aspects of the invention have computer-executable componentsfor managing consent between a client and at least one network server.The client and the network server are coupled to a data communicationnetwork. And the network server provides a service to a user via theclient. The computer-readable media include a profiling component forstoring user-specific information associated with the user. Thecomputer-readable media also include a consent component for receiving arequest from the service provided by the network server for userinformation associated with the user and for consent to use therequested user information. The consent component is further configuredto determine, in response to the request for consent, if the requesteduser information is stored in the profiling component. Thecomputer-readable media further include a user interface component forcollecting the requested user information that is not included in theprofiling component from the user. The consent component is configuredto receive the requested user information provided by the user via theuser interface component and to allow access by the service to thereceived user information.

Computer-readable media having computer-executable instructions forperforming methods of managing consent embody further aspects of theinvention.

Alternatively, one embodiment of the invention may comprise variousother methods and apparatuses.

Other features will be in part apparent and in part pointed outhereinafter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an exemplary network environmentin which one embodiment of the present invention may be utilized.

FIG. 2 is a diagram illustrating an exemplary interaction between clientcomputer systems, affiliate servers, and central server of FIG. 1.

FIGS. 3A and 3B are exemplary flow diagrams illustrating process flowaccording to one embodiment of the invention.

FIG. 4 is an exemplary flow diagram illustrating further aspects ofprocess flow according to one embodiment of the invention.

FIG. 5 is an exemplary flow diagram illustrating yet further aspects ofprocess flow according to one embodiment of the invention.

FIG. 6 is an exemplary flow diagram illustrating yet further aspects ofprocess flow according to one embodiment of the invention.

FIG. 7A to 7G illustrate exemplary user interfaces for profile andconsent accrual according to embodiments of the invention.

FIG. 8 is a block diagram illustrating an exemplary computer-readablemedium according to one embodiment of the invention.

FIG. 9 is a block diagram illustrating an exemplary embodiment of asuitable computing system environment in which one embodiment of theinvention may be implemented.

Corresponding reference characters indicate corresponding partsthroughout the drawings.

DETAILED DESCRIPTION OF THE INVENTION

Referring now to the drawings, FIG. 1 illustrates an exemplary networkenvironment in which embodiments of the present invention may beutilized for managing permissions and user profile information.Embodiments of the invention relate to cross-internet collaborationbetween web sites as part of, for example, a distributed, multi-siteuser authentication system. Such services provide a user with theability to access one or more participating web sites or resources witha single sign-in. Although the participating sites (referred to hereinas “affiliates” or “affiliate sites”) maintain control over permissions,they use the authentication service rather than hosting and maintainingtheir own proprietary authentication systems. The related sites orservices are referred to herein as a “service group” or “shared servicesgroup” because they represent a group of independent sites IDs thattogether provide a user with a set of services. Shared services groups,however, need not employ the same policies regarding permissions. Asused herein, “policy group” or “consent group” refers to a predefinedgroup of sites (or applications generally) that have a sharedpermissions set, that is, they share a common set of permissionstandards (e.g., a common privacy policy).

As a part of the single sign-in service, the user can choose to storeinformation in a user profile. Typical user profile information(attributes) includes name, address, gender, occupation, preferredlanguage, credit card information, billing address, shipping address,telephone numbers, and the like. At the user's option, the sign-inservice makes all or part of the user profile information available toparticipating sites visited by the user. In one embodiment, the user isredirected from the sign-in service back to the desired affiliate sitewith an encrypted authentication ticket and profile informationattached. This enables affiliate sites to customize and enhance userexperience without having to prompt for information.

In FIG. 1, one or more client computer systems 162 are coupled to a datacommunication network 164. In this exemplary embodiment of theinvention, the network 164 is the Internet (or the World Wide Web). Butthe teachings of the present invention can be applied to any datacommunication network. Multiple affiliate servers 166 are also coupledto network 164. The affiliate servers 166 may be referred to as “webservers” or “network servers” generally.

A central server 170 coupled to network 164 allows communication betweenitself, client computer systems 162, and web servers 166. In operation,one or more client computer systems 162 can access affiliate servers 166via network 164. Although sometimes referred to as an “authenticationserver,” “login server,” or “profile server” in connection with FIG. 1,the central server 170 in the illustrated embodiment is also a webserver capable of interacting with web browsers and other web servers.In this example, server 170, client computer systems 162, and webservers 166 communicate data among themselves using the hypertexttransfer protocol (HTTP), a protocol commonly used on the Internet toexchange information.

The sites of affiliated servers 166 may exhibit the privacy statement ofthe hosting service, which indicates that they are under the auspices ofthe same policy and, thus, changes made to data usage will impact thesites. Nevertheless, a particular content provider's policy could bechanged without affecting the policy of the related services.

FIG. 1 further illustrates a database 172 coupled to server 170. In oneembodiment, the database 172 stores information (i.e., credentials)necessary to authenticate a registered user of one of the clientcomputer systems 162 (as well as other users on the network). Thedatabase 172 also maintains a profile store for registered users andidentifies which elements of the user profile information should beprovided to a particular affiliate server 166 when the user accesses itsservice. In general, a credential is a means for generating anauthenticated reference to a single account identifier. For example, anEASI (E-mail As Sign-In) sign-in name and password, a mobile phonenumber and PIN, and a biometric signature are credentials that can beassociated with the same profile data. The sites/services of affiliatedservers 166 may employ a common privacy statement of a hosting serviceor use entirely different policies.

Although database 172 is shown in FIG. 1 as a single storage unitseparate from central server 170 for convenience, it is to be understoodthat in other embodiments of the invention, database 172 may be one ormore memories located within or separate from server 170. In a federatedenvironment, for example, a plurality of servers 170 may be used toprovide authentication, shared services management, policy andpermissions management, and the like.

The server 170, as described herein, may be part of an authenticationsystem that authenticates a user of client computer 162 seeking accessto a particular one of the affiliate servers 166. In this embodiment,server 170 first requests authenticating login information from theuser, such as the user's login ID and password. If the user issuccessfully authenticated, the server 170 of FIG. 1 routes the user'sclient computer 162 to the appropriate affiliate server 166 forperforming a desired service for the user.

In one embodiment, an “affiliate server” is a web server that has“registered” or otherwise established a relationship or affiliation withcentral server 170. A particular affiliate server 166 includes a codesequence (not shown) that allows the affiliate server to communicatewith server 170 when a user (who is also registered with server 170)requests access to affiliate server 166. Additional details regarding anexemplary authentication process and the interaction between clientcomputer 162, affiliate servers 166, and server 170 are provided below.

Before executing the authentication process, both the user of clientcomputer system 162 and the operator(s) of affiliate servers 166“register” with server 170. This registration is a one-time process thatprovides necessary information to the authentication system. Accordingto one embodiment of the invention, this registration also provides theuser with his or her first opportunity to grant consent for the sharingof certain personal information. The user of client computer system 162registers with server 170 by providing information about the user and/orclient computer system 162, such as, the user's name, mailing address,and e-mail address. As part of the user registration process, the useris assigned (or selects) a login ID, which is a common login ID, used toaccess an affiliate server (e.g., server 166). The login ID may also bereferred to herein as a “username,” “member name,” or “login name.”

Additionally, the user selects a password associated with the login IDthat is used for authentication purposes. After registering and logginginto server 170, the user can visit an affiliate server 166 (i.e.,affiliate servers that are also registered with the same authenticationserver) without additional authentication and often without reenteringuser information that is already included in the associated userprofile. One embodiment of the present invention sets forth identifyingthe user account, or profile, by a unique account identifier.

The central server 170 of FIG. 1, i.e., the authentication server inthis embodiment, validates the username/password provided by the user.Server 170 handles the authentication response by comparing the logindata to the entries in database 172. If the username and password matchan entry in the database 172, the user is authenticated. A uniqueidentifier (e.g., Passport Unique Identifier (PUID)) and a user profilecorresponding to the authenticated user are extracted from the database.In this embodiment, when a user registers an account, the account isassigned a PUID that becomes the unique identifier for the account. ThePUID is, for example, a 64-bit number that the authentication serversends (e.g., encrypted) to affiliate servers 166 as the authenticationcredential when the user signs in. This unique identifier makes itpossible for the sites to determine whether the user is the same personfrom one sign-in session to the next.

When the user later visits an affiliate server 166 after central server170 assigns a unique identifier to his or her account, the affiliateserver 166 may desire the user to submit certain user-specificinformation in order to allow the user access to its contents orservices. In this embodiment of the invention, affiliate server 166 mayfirst request the user-specific information from central server 170.After receiving the request from affiliate server 166, central server170 may access database 172 to obtain a user profile associated with theuser. If the user profile associated with the user already includes theuser-specific information requested by affiliate server 166, centralserver 170 may communicate the requested user-specific information toaffiliate server 166 without prompting the user to submit theinformation. On the other hand, if the requested user-specificinformation is not included in the user profile, central server 170 mayprovide a consent UI to the user via a browser of client computer system162. This consent UI includes open fields for the user to enter therequested user-specific information. If the user enters and submits therequested user-specific information to central server 170 via theconsent UI, then he or she is allowed access to the contents or servicesprovided by affiliate server 166. In addition, central server 170 willallow affiliate server 170 access to the submitted user-specificinformation. Central server 170 will further update the user profilewith the submitted user-specific information. As can be seen, thisembodiment of the invention advantageously allows a service toincrementally accrue consent to use information associated with a userduring the user's experience with the service.

A service requesting user-specific information may belong to one or moreadministrative groups. Generally, administrative groups support thescenarios in which a user who has authority over the authorizationsettings or permissions of one or more other users. Such groups include,for example, parents, managers, users who control multiple credentials,and domain space administrators. One of several administrative groups, aservice group comprises site IDs representative of related sites on thenetwork that work together to provide the user with a consistent set ofservices. Members of a service group, however, need not share the sameprivacy statement. When this is the case, the user typically consents tothe sharing of user-provided data with a particular policy grouprepresented within the service group. There should be a contractualarrangement providing the user with a known set of services.

One such situation is when a network of Internet services providespremium content through an affiliated site. Operational information thatmay be maintained by one site but accessible to both the one site andanother related site indicates that the user has, for example, a premiumcontent subscription. This information allows the user to move betweencontent providers without having to re-authenticate or prove membershipas a premium content subscriber. Further, multi-company corporations canbe represented as a service group when they do not share a corporateprivacy statement. This might be when a financial company owns bothbanks and insurance companies and it wants the user to be able to movebetween the different companies without having to re-authenticate orprove membership.

On the other hand, a policy group comprises sites/services that operateunder a shared privacy or other permissions policy. The policy group,which is another form of administrative group, implements first timelogin consent scenarios. By grouping applications, such as particularweb services, having the same privacy policy, an embodiment of theinvention allows a user to grant consent to share information withmembers of the policy group the first time the user signs in to a memberof the group. If a particular site does not share a privacy statementwith another site, then its site ID can be considered a policy group ofone.

In one embodiment, member policy groups do not need to be listed in agroup store. During the consent process, the server 170 of FIG. 1 canlook to determine whether the site ID for the affiliate site 166requesting information is a member of a policy group. In general, thedatabase 172 associated with server 170 stores the operationalinformation described above as well as the site IDs for the variousservice group and policy group members. If there is no association, thenthe site ID is a single member policy group.

In the context of shared services management, the user profile includesinformation used to represent participating site/user-specificinformation (e.g., whether or not the user has premium services such asthose provided through an Internet portal or online service). One methodfor enabling participating sites/services to share information abouttheir users with members of the site/service group is for theauthentication system to include these information “bits” in a profilecookie. For instance, a premium content bit for an Internet servicesnetwork allows sites on the services network to know that the user has apaid subscription, without having to make additional server-to-servercalls. This information may be built into the profile cookie regardlessof the site at which the user signs in and is independent of consentsettings.

FIG. 2 is a diagram illustrating an exemplary implementation of oneembodiment of the present invention and the interaction between server170, multiple client computer systems 162, and at least one affiliateserver 166. The illustrated example of FIG. 2 describes the situation inwhich the user of client computer system 162 has not yet logged intoaffiliate server 166 and has not yet been registered or authenticated byserver 170. The lines in FIG. 2 labeled “A” through “I” represent theflow of information or activities during the process. The arrows on thelines indicate the direction of the process flow. In this example, thelabel “A” represents the beginning of the processes and the label “I”represents the end of the process.

In the exemplary process flow of FIG. 2, Service A and Service B formone shared services group. Service A and Service C form another servicegroup. Service A and Service B also share a common privacy policy and,thus, are in a policy group together. The user, shown at client computer162, navigates to a first selected service, namely, Service A (see A1).As an example, Service A represents an Internet portal service to whichthe user is signing in for the first time. Server 170 initiates sign-inand seeks first time consent from the user to disclose or use certaininformation in the user's profile (see A2/A3). The central server 170also either stores the user's credentials for the first time or verifiesthe previously stored information (see B). Further, server 170 creates aticket including: (a) user profile information that the user has agreedto share with Service A; (b) operational information specific to ServiceA; and (c) operational information that is shared between Service A andService B (e.g., the user's status as a premium subscriber to ServiceB's content). If the shared services groups are established ahead oftime, the user is signed in to Service A (see C1/C2) with both Service Aspecific and Service B and Service C shared operational information. Inthis instance, FIG. 2 further represents the user's first time consentto the privacy policy of Service A (see A2/A3).

When the user navigates to a content provider such as a Service B (seeD1), server 170 silently authenticates the user (see D2/D3) inasmuch asthe user is navigating within a shared services group. Moreover, ServiceA and Service B share a common privacy policy so that the user need notgrant separate permission to Service B. In a similar manner, the server170 as shown in FIG. 2 verifies the user (see E) and creates a ticketincluding: (a) user profile information that the user has agreed toshare with Service B; (b) operational information specific to Service B;and (c) operational information that is shared between Service A andService B. Central server 170 permits the user to sign in to Service B(see F1/F2) with both Service B specific and Service A sharedoperational information. But Service B does not have access toinformation in the client specific to Service A or shared by Service Aand Service C. The user need not know that the system has routed him orher to another site because of the shared services and shared privacypolicy arrangements.

In this exemplary process flow of FIG. 2, the user navigates to ServiceC (see G1) and is asked to re-authenticate (see G2/G3) because theimmediately preceding site was in a different shared services group. Aspart of an authentication system, central server 170 verifies the user(see H) and creates a ticket including: (a) user profile informationthat the user has agreed to share with Service C; (b) operationalinformation specific to Service C; and (c) operational information thatis shared between Service A and Service C. The server 170 signs in theuser to Service C (see I1/I2) with both Service C specific and Service Ashared operational information. As above, Service C does not have accessto information specific to Service A or shared by Service A and ServiceB. In the event this is the user's first visit to Service C, the userwill again go through a first time consent process because Service C isnot in the policy group with Services A and B. Even if Service Cbelonged to the same service group as Services A and B, the consentprocess would be necessary because Service C employs a different privacypolicy in this example.

According to one exemplary embodiment of the invention, database 172stores

guage (XML) file (hereinafter policygroup.xml) associated with aparticular policy group. The policygroup.xml file includes informationspecific to the policy group and is utilized by central server 170 toperform authentication, shared services management, policy andpermissions management, and the like. Table 1 provides descriptions ofexemplary fields stored in the policygroup.xml file. TABLE 1 Format ofthe Policygroup.xml File Field Description Friendly Name A stringrepresenting the name of the policy group. Group ID A unique numericidentifier for the policy group. Group Type A numeric identifier thatindicates the type of the policy group. Group Owner A numeric identifierfor the owner of the policy group. This is the PUID of the user who isacting as the administrator for this policy group. Privacy Policy Apointer to the privacy policy for Uniform Resource this policy group.Locator (URL) Privacy Policy A version number of the privacy policy forVersion Number this policy group. Default Profile A list of profileattributes and intentions Attributes and that are used during profileand consent Intentions accrual at a specific site in the policy group ifthe site has not specified a set of overriding profile attributes andintentions. Retention A description of how long sites in the policygroup intend to use the accrued profile attributes. There is oneretention per policy group. Default Value A sales pitch to get users toshare Proposition information. This is used when a specific site has notspecified an overriding value proposition. Edit External Data A pointerto a web page for users to edit URL site-specific attributes that arenot stored in the user profile. Account Removal A pointer to a web pagefor users to URL remove site-specific attributes that are not stored inthe user profile.

In another exemplary embodiment of the invention, database 172 alsostores an XML file (hereinafter site.xml) associated with a particularsite of the policy group. According to this embodiment of the invention,the site.xml file includes information specific to the particular siteand is also utilized by central server 170 to perform authentication,shared services management, policy and permissions management, and thelike. Table 2 provides descriptions of exemplary fields stored in thesite.xml file. TABLE 2 Format of the Site.xml File Field DescriptionSite Name A string representing the name of the site. Home Page Apointer to the site homepage. URL Profile A list of profile attributesand site-specific attributes Attributes desired by the site. The sitecan define additional site- and Site- specific attributes in addition tothe core profile attributes Specific defined by server 170. In thedetailed description of the Attributes invention hereinafter, the term“attributes” may refer both to profile attributes and site-specificattributes. Server 170 defined profile attributes are specified by IDs,and site-specific attributes are specified by name strings. If profileattributes are specified in the site.xml file, they override the defaultprofile attributes specified in the policygroup.xml file for the policygroup of this site. There is also a “PolicyGroupDefaults” abstractattribute that allows sites to include the default profile attributesspecified by the policygroup.xml file. Value A sales pitch to get usersto share information. If a value proposition proposition is specified inthe site.xml file, it overrides the default value proposition specifiedin the policygroup.xml file for the policy group of this site.Intentions A description of how the accrued profile attributes andsite-specific attributes will be used by the site. If intentions arespecified in the site.xml file, they override the default intentionsspecified in the policygroup.xml file for the policy group of this site.Policy A unique numeric identifier for the policy group to which Groupthe site belongs.

In one embodiment of the invention, one policy group cannot be a memberof another policy group. And sites can be in one policy group at a time.According to another embodiment of the invention, a site may move fromone policy group to another. But if the user has previously grantedconsent for the original policy group to access the profile attributesstored in the user profile of the user, this consent remains with theoriginal policy group. That is, the moved-away site can no longer accessthe profile attributes unless the user also grants consent for the newpolicy group to access the stored profile attributes.

As shown in Tables 1 and 2, the policygroup.xml file and the site.xmlfile may specify a list of profile attributes that are desired by a sitewhen the user attempts to sign in to the site. According to anembodiment of the invention, if the site has specified the desiredprofile attributes in the layout section of its site.xml file, theseprofile attributes override the default profile attributes specified inthe policygroup.xml file for the policy group to which the site belongs.Additionally, the site may specify an empty layout section in thesite.xml file, which means that the site does not desire a profileattribute and that the site will not accrue information from the user.And the site may include in its site.xml file a directive (thePolicyGroupDefaults abstract attribute) to specify the default profileattributes of the policygroup.xml file as its desired profileattributes. In such a scenario, a union of both sets of profileattributes is used for the site. That is, the site has specified that itdesires both the profile attributes specified in the site.xml file andthat specified in the policygroup.xml file.

Again, when the user attempts to access one of the services provided byone or more affiliate servers 166, he or she may first be directed tocentral server 170 for authentication. If the user does not have acredential stored in database 172, server 170 may desire the user toregister with server 170 before allowing the user to access the service.That is, server 170 may host both the registration and authenticationservices (e.g., EASI). In one embodiment, the services hosted by server170 also belong to a policy group, which may be the same policy groupthat one or more services of affiliate servers 166 belong to. As part ofthe registration process, in addition to the profile attributes desiredby the service (which are specified in the site.xml of the serviceand/or in the policygroup.xml of the policy group to which the servicebelongs), server 172 may also mandate certain profile attributes fromthe user. The set of profile attributes desired by server 170 and theassociated intentions and retentions are specified in an XML file(hereinafter namespace.xml) associated with server 170. As such, thelist of profile attributes that the user needs to provide duringregistration is a union of profile attributes specified in thenamespace.xml file and the site.xml file or that specified in thenamespace.xml file and the policygroup.xml file if the overridingprofile attributes are not specified in the site.xml file.

According to one embodiment of the invention, after the user completesthe registration process by providing the desired profile attributes,one or more consent records are stored in database 172 indicating thatthe user has granted consent for the service (and the policy group towhich it belongs to) and server 170 to use the provided profileattributes. Furthermore, server 170 creates and stores a user profileincluding the profile attributes provided by the user. According toanother embodiment of the invention, a set of simple object accessprotocol (SOAP) application programming interfaces (APIs) may beutilized to manipulate the consent records and other consent settingsprogrammatically. In this embodiment of the invention, a particular SOAPrequest is accompanied by a valid authentication ticket for the profileservice. This ticket is in the SOAP message itself or in the HTTPheaders. For security reasons (e.g., a client-side script from a hostileweb site can fabricate SOAP requests and cause existing tickets to beautomatically attached in the outgoing request headers), ticketsarriving inside a cookie header are ignored.

APPENDIX A provides specific examples of the SOAP APIs and theircorresponding signatures.

As discussed above, a set of intentions is associated with a particularprofile attribute or site-specific attribute desired by the service. Theintentions describe how a service intends to use the attributes providedby the user. In one embodiment of the invention, a particular intentionis represented as a bit mask. Accordingly, the bit mask representationfor the set of intentions associated with a particular attribute can beobtained by applying an OR operation to the individual bit maskrepresentations of the intentions associated with the attribute. Thisbit mask representation for the set of intentions associated with theattribute can then be stored in a consent record.

In an alternative embodiment of the invention, an intention is stored inthe site.xml, policygroup.xml and/or namespace.xml files as a numericvalue instead of a string value. In order to prevent services providedby affiliate servers 166 from creating their own intentions, server 170may define a string value for one or more numeric intention values. Assuch, the services are forced to adopt the intentions defined by server170. Table 3 illustrates exemplary string values of the intentions andtheir corresponding numeric values. TABLE 3 Exemplary Intention ValuesNumeric Value String Value 1 Provide targeted content and advertisingduring your current visit. 2 Complete the task that you have asked us todo. 3 To help us maintain the site/service. 4 To help us evaluate andreview our products, content or service. 5 To help us understand whatour users such as you like to do when they use our site/service. 6Provide targeted content and advertising based upon what we know aboutusers such as yourself. 7 To help us understand what you, as anindividual, like to do when you visit our site/service. 8 Providetargeted content and advertising based upon what we know about you andhow you use our site or service. 9 To contact you in order to notify youof updates to the site or service. 10 To contact you in order to promoteproducts or services. 11 Share information with third parties accordingto our privacy policy, which can be viewed at (URL). 12 For some purposenot covered by these statements.

The user may grant consent for the service to use a particular attributefor a particular intention. When such consent is granted by the user,members of the policy group to which the service belongs may also usethe attribute for this particular intention. As such, the consent recordmay indicate the following:

-   PolicyGroup=1-   attribute=email, intentions=1, 3-   attribute=gender, intentions=1

According to one embodiment of the invention, if the user signs in todifferent services in the same policy group, and if those services havedifferent intentions for the same attribute, the user should re-grantconsent for that attribute. For example, if the user grants consent toService A in Policy Group 1 for gender and occupation with intention 2,and then signs in to Service B in Policy Group 1, which desires genderwith intention 3, then the user is needed to grant consent to Service Bfor gender with intention 3. After the user grants such consent, theconsent record would indicate the following:

-   PolicyGroup=1-   attribute=gender, intentions=2, 3-   attribute=occupation, intentions=2    It is noted that the actual attribute value is not stored in the    consent record. Instead, the consent record stores the numeric    identifier of the attribute.

In contrast to intentions, retentions specify the length of time thatmembers of a policy group intend to keep information obtained from theuser. In addition, unlike intentions, retentions apply to the entirepolicy group instead of individual members and apply to the entire setof attributes instead of individual attributes. But similar tointentions, retentions are stored in the site.xml, policygroup.xml,and/or namespace.xml files as numeric values instead of string values.And server 170 may define the string values for the numeric retentionvalues to prevent services from creating their own retentions. Table 4illustrates exemplary string values of the retentions and theircorresponding numeric values. TABLE 4 Exemplary Retention Values NumericValue String Value 1 Information is not retained beyond the currentsession. 2 Information is retained no longer than necessary to completethe user request. 3 Information is retained beyond task completion inorder to be compliant with one or more legal requirements. 4 Informationis retained according to the business practices of the site. The sitedoes have a data destruction policy which can be viewed at (URL). 5Information is retained for an indefinite period of time and may or maynot be destroyed.

There may be certain inherent dependencies between profile attributes.For example, the location profile attributes (country, zip, region, timezone) are inherently dependent on each other. Such dependencies mayaffect how services request these profile attributes and what are sentto the services. For example, server 170 may validate zip code based onthe provided country and region information. Server 170 may alsovalidate time zone based on the country information. So during profileand consent accrual, it may be desired that certain location profileattributes be provided in groups.

To ensure that the services understand these groups and to preventserver 170 from having to write validation codes that check for missingdependent profile attributes, group names may be defined for theservices to represent these profile attribute groups. Table 5 showsexemplary dependencies between location profile attributes and exemplarygroup names for services to include in their site.xml files. TABLE 5Group Names for Interdependent Profile Attributes Then collect and sendto If service wants: service: Group Name for site.xml Postal CodeRegion + Country + RegionCountryPostalcode Postal Code Region Region +Country RegionCountry Time Zone Country + Time Zone CountryTimezone

FIGS. 3A and 3B illustrate an exemplary operational flow forincrementally accruing user profile and consent according to oneembodiment of the invention. FIGS. 3A and 3B involve a user who isvisiting Service A hosted by one or more affiliate servers 166. Beforethe user is allowed access to Service A, Service A desires certaininformation regarding the user and thus requests a user profile of theuser from central server 170 (e.g., via a SOAP API call). After the useris directed to server 170 and the login information (e.g., user email)is validated by server 170, server 170 at 302 determines if the user hasalready granted consent for Service A to use the profile attributesstored in the user profile. If the user has already granted consent toService A, server 170 continues to 304 to determine if the requestedprofile attributes (i.e., the desired information) are in the userprofile. If server 170 determines that the requested profile attributesare already in the user profile, then no profile and consent accrual isneeded. In this case, server 170 may deliver the user profile to ServiceA.

Before server 170 delivers the user profile, it is determined at 306 ifService A is a legacy mode service. According to one embodiment of theinvention, a legacy mode service does not allow the user to sign in tothe service until he or she grants consent to the service. In contrast,a non-legacy mode service may allow the user to sign in and use its sitewithout accruing the profile attributes stored in the user profile. Inone embodiment of the invention, a flag called ProfileViaPOST embeddedin the SOAP request is used to determine if Service A is in legacy modeor not. If this flag is set to a value of 1, Service A is not in legacymode. As such, the user profile is delivered to Service A as a signedXML blob via HTTP POST over secure sockets layer (SSL). IfProfileViaPOST is not present or is set to a value of 0, Service A is inlegacy mode. This means that the user profile is delivered to Service Aas a profile cookie (e.g., a “p” parameter in the query string of thereturn URL of Service A). In addition, accompanying the profile cookieis an authentication ticket that authenticates the user for Service A.After the user profile is delivered to Service A, the user is redirectedback to Service A from server 170.

According to one embodiment of the invention, the user profile deliveredto Service A may include the entire profile attributes that the user hasgranted consent to the policy group to which Service A belongs. Whenmultiple legacy mode services in the policy group shares an encryptionkey, these services should check the profile cookie to ensure that theyare getting the desired profile attributes. If the correct attributesare not present, Service A may direct the user to server 170 to get thecorrect profile cookie. This might be necessary because the user mayhave previously signed in to another service in the policy group thatdesires fewer or different profile attributes. If this is the case, theprofile cookie may be written with the profile attributes desired by thefirst service, which may be a subset of the profile attributes desiredby Service A. When the user goes to Service A, the existingauthentication ticket and profile cookie may automatically sign in theuser to Service A. But since Service A desires different or more profileattributes than those present in the profile cookie, the user should bedirected to Service A to create a new profile cookie with the properprofile attributes (i.e., the profile attributes desired by bothservices).

Back to 302 and 304, if server 170 determines that the user has notalready granted consent to Service A or that the requested profileattributes are not available in the user profile, server 170 proceeds to312 to determine the value of Service A's KPP parameter read from thequery string. In one embodiment of the invention, the KPP parameterspecifies the parental consent requirements of children's privacy lawssuch as the Children's Online Privacy Protection Act (COPPA) and canhave a range of values. In one embodiment of the invention, a KPP valueof 0 indicates that Service A does not wish to comply with thechildren's privacy laws and thus is not a KPP service. In such ascenario, server 170 may proceed to 314. On the other hand, a non-zeroKPP value indicates that Service A complies with the children's privacylaws (and thus a KPP service). In this case, server 170 may proceed to aminor consent process at 316, which is generally illustrated in FIG. 5.

At 314, server determines if the user profile of the user is active.According to one embodiment, the user may have made a decision onwhether to have an active profile or an inactive profile duringregistration. An inactive profile means that profile attributes are notaccrued from the user and that the user profile includes no profileattributes. In contrast, if the user has an active profile, profileattributes will be accrued and stored in the user profile depending onthe consent granted by the user.

In one embodiment of the invention, if server 170 determines that theuser profile is inactive, it continues to a consent process withinactive profile at 318, which is generally illustrated in FIG. 4. Ifthe user profile is active, a consent UI with active profile isdisplayed to the user at 320. According to one embodiment of theinvention, the consent UI is displayed to the user via a browser of oneof the client computer systems 162 as a hypertext markup language (HTML)page. Included in the consent UI is a number of open fields for entry ofprofile attributes desired by Service A (and potentially additionalprofile attributes desired by the policy group to which Service Abelongs). And profile attributes already stored in the user profile aredisplayed in the consent UI in non-editable form. According to oneembodiment of the invention, Service A may specify in its site.xml filea list of site-specific attributes that it wishes to collect from theuser. The site-specific attributes are specific to Service A andaccordingly not stored in the user profile (instead, they may be storedin a database of Service A). If Service A has specified a list ofsite-specific attributes in its site.xml file, the consent UI mayinclude open fields for entry of these site-specific attributes. Thesefields are displayed in the consent UI in a visually distinct way toinform the user that they are not part of the user profile.

Typically, the username that the user used to sign in to Service A maybe the same as the alias of the user's email address stored in the userprofile. And it is common for a service to allow the user to sign inusing his or her email address. According to embodiments of theinvention, if Service A specifies the user's email address or usernameas a desired profile attribute, and if the username is the same as theemail alias, the consent UI may include a open field for the user toenter the email address instead of the username. In this embodiment ofthe invention, if the user submits his or her email address to server170, Service A has been effectively granted consent to use the usernameof the user.

The consent UI may further provide a value proposition describing whythe user should provide the requested attributes to Service A. Asindicated at 322, a user-selectable option (e.g., an HTML link) allowsthe user to review intentions and retentions associated with therequested and previously stored profile attributes. Upon selection ofthe user-selectable option at 322, server 170 at 324 provides anintentions and retentions UI to the user. The intentions and retentionsUI displays a list of requested and previously stored profile attributesand the corresponding intentions and retentions. The intentions andretentions for site-specific attributes desired by Service A and for theprofile attributes desired by the policy group of Service A may also bedisplayed in the intentions and retentions UI. In one embodiment,attributes with the same intentions are grouped together in theintentions and retentions UI. And the intentions and retentions UI maydisplay a list of services belonging to the policy group of Service A.

As an example, the intentions and retentions include a user-selectableoption (e.g., an HTML link) for the user to view the privacy policyassociated with the policy group to which Service A belongs, asindicated at 326. Upon selection of the user-selectable option at 326,server 170 at 328 may provide the privacy policy to the user (e.g., viaa web page). As indicated at 330, if the user selects a “back” optiondisplayed on the privacy policy page or in the intentions and retentionsUI, he or she is directed back to the consent UI.

According to one embodiment of the invention, the consent UI alsoincludes an “edit profile” option. Upon selection of the edit profileoption at 332, the user is directed to an edit profile process at 334.At the beginning of the edit profile process, server 170 provides anedit profile UI (not shown) to the user. The edit profile UI includes alist of profile attributes currently stored in the user profile andprovides open fields for the user to edit or update the currently storedprofile attributes. After editing/updating the profile attributes andconfirming the changes, a consent record is stored in database 172. Theconsent record indicates that Service A (and other members of the policygroup of Service A) is granted consent to access the edited/updatedprofile attributes. Accordingly, Service A may request the same profileattributes without another consent UI in the future. The edited/updatedprofile attributes are further stored in the user profile. Accordingly,if the user selects an option to go back to the consent UI, the consentUI will now display the edited/updated profile attributes. In contrast,if the user goes back to the consent UI without confirming the changes,the consent UI will display the old profile attributes previously storedin the user profile. It is noted that if the user empties profileattributes in the edit profile UI and confirms the changes, the userprofile then becomes inactive.

After entering the desired attributes in the open fields displayed inthe consent UI, the user may select an option at 336 to continue theconsent process. Upon selection of the option, server 170 determines at338 if the user has entered new profile attributes. If the user hasentered new profile attributes, server 170 further at 340 determines ifthe user has chosen to save the newly entered profile attributes bychecking a checkbox displayed in the consent UI. If the user has chosento save the newly entered profile attributes, server 170 proceeds to 342to save the newly entered profile attributes in the user profile.Furthermore, server 170 at 344 stores a consent record in database 172indicating that the user has granted consent for Service A to use thenewly entered profile attributes. If the user has also granted consentfor site-specific attributes, the consent record also indicates thatService A has been granted consent to use the site-specific attributes(and accordingly these site-specific attributes may not subsequently beaccrued again). After the consent record is stored in database 172 (andif no new profile attribute is entered or if the user has not chosen tosave the new profile attributes), server 170 proceeds to 306 todetermine the mode of Service A. Server 170 then delivers the userprofile to Service A as a function of the mode of Service A.

It is noted that in one embodiment of the invention, if the user grantsconsent to Service A, then he or she is effectively granting consent tothe policy group to which Service A belongs. In other words, the memberservices of the policy group of Service A will be able to access theprofile attributes stored in the user profile.

As indicated at 346, the consent UI further includes an option for theuser to cancel the consent process. Upon selection of the option at 346,server 170 determines at 348 if Service A is a legacy mode service. IfService A is not a legacy mode service, server 170 at 350 delivers anHTTP POST to Service A with “cancel” in the body of the POST. If ServiceA is a legacy mode service, server 170 at 352 redirects the user back toService A without an authentication ticket and profile cookie.Accordingly, if Service A is a legacy mode service, the user is notallowed to sign in to Service A. It is noted that according to oneembodiment of the invention, even if the user cancels the consentprocess, prior existing consent to Service A may still remain (i.e.,prior consent record is not removed). Accordingly, Service A may stillbe able to access profile attributes (and site-specific attributes) thatService A had previously been granted consent to use.

The consent UI may be provided to the user at subsequent visits toService A under several scenarios. First, if Service A starts desiring adifferent set of attributes (including site-specific attributes) fromthose for which consent has already been granted, another consent UI maybe provided to the user to accrue consent for the new set of attributes.Second, consent accrual may be needed again if Service A changes theintentions and retentions for attributes (including site-specificattributes) for which consent has already been granted, unless the userhas granted consent for another service within the same policy group touse the attributes under the new intentions and retentions. For example,if the user has granted consent for Service A to use the user email forcontact purpose, and subsequently Service A decides to use the email foradvertising purpose, the consent UI will show up again when the usersubsequently visits Service A in order to accrue consent for Service Ato use the email for advertising purpose. Third, if the user deletes oneor more of the profile attributes from the user profile to which he orshe has already granted consent to Service A, the consent UI may beprovided to the user during subsequent visits to Service A in order toaccrue the deleted but desired profile attributes.

FIG. 4 illustrates an exemplary operational flow for consent accrualwith an inactive profile according to one embodiment of the invention.After server 170 determines that the user profile of the user is aninactive profile (e.g., at 314 of FIG. 3A), server 170 may provide aconsent UI with inactive profile to the user via a browser of one ofclient computer systems 162. The consent UI is similar to the consent UIof FIGS. 3A and 3B and includes an option for the user to reviewintentions and retentions associated with the desired and previouslystored profile attributes (as well as site-specific attributes). Uponselection of the option at 404, server 170 may at 406 provide anintentions and retentions UI to the user. The intentions and retentionsUI is also similar to the intentions and retentions UI illustrated inFIGS. 3A and 3B and displays intentions and retentions associated withthe attributes as well as a list of services belonging to the policygroup to which Service A belongs. The intentions and retentions UI alsoincludes a user-selectable option for the user to view the privacypolicy of the policy group of Service A. Upon selection of the option at408, server 170 may at 410 provide the privacy policy to the user via aweb page. As shown in FIG. 4, by selecting a “back” option at 412, theuser may return to the consent UI from the privacy policy page or theintentions and retentions UI.

The consent UI includes a list of open fields for the user to enter therequested attributes and an option for the user to continue the consentprocess. Upon selecting the option to continue at 414, server 170 at 416determines if the user has entered new profile attributes. If the userhas entered new profile attributes, server 170 determines at 418 if theuser has decided to enable/activate the user profile by checking an“enable profile” checkbox displayed in the consent UI. If the user hasdecided to enable/active the user profile, server 170 at 420 creates theuser profile with the entered profile attributes and stores a consentrecord in database 172 indicating that Service A has been grantedconsent to use the newly entered profile attributes (as well as thenewly entered site-specific attributes). After the user profile iscreated and the consent record is stored (or if no new profile attributeis entered or if the “enable profile” checkbox is not checked), server170 determines at 422 if Service A is a legacy mode service. If ServiceA is a legacy mode service, server 170 at 424 redirects the user toService A with a profile cookie and authentication ticket to allow theuser to sign in to Service A. If Service A is not a legacy mode service,server 170 at 426 delivers the user profile to Service A as a signed XMLblob via HTTP POST over SSL.

In one embodiment of the invention, the consent UI also includes anoption for the user to cancel the consent process. If the option isselected by the user at 428, server 170 at 430 then determines ifService A is a legacy mode service. If Service A is a legacy modeservice, server 170 at 432 redirects the user back to Service A withoutan authentication ticket and profile cookie. If Service A is not alegacy mode service, server 170 at 434 delivers an HTTP POST to ServiceA with “cancel” in the body of the POST. It is noted that the differencebetween the consent process with an active profile and the consentprocess with an inactive profile is that with an inactive profile, theuser cannot edit stored profile attributes. This is because an inactiveprofile has empty fields (i.e., it does not store a profile attribute).

Referring now to FIG. 5, illustrated is an exemplary operational flowfor the minor consent process according to one embodiment of theinvention. In one embodiment of the invention, the consent processillustrated in FIG. 5 can be applied to a managed user account such as aparent or other responsible person granting consent for a minor.According to the embodiment of the invention, after server 170determines that Service A is a KPP service at 312 of FIG. 3A, server 170then at 502 determines if Service A complies with comprehensive parentalconsent requirements. This can be determined from the KPP parameter ofService A. For example, a KPP value of 3 may indicate that the servicewishes to comply with the most restrictive parental consent requirements(e.g., as specified by COPPA). If Service A does not wish to comply withsuch comprehensive parental consent requirements, server 170 proceeds to504 to determine if the user is a minor. If the user is not a minor,then server 170 at 506 proceeds to a normal consent process, whichbegins at 314 of FIG. 3A. If the user is a minor, then server 170proceeds to a parent granting minor consent process at 508.

The parent granting minor consent process begins by providing a UIasking the user if the parent or other responsible person of the user ispresent with the user. If the user indicates that the parent (or otherresponsible person) is currently present with the user, server 170renders a request for the parent to sign in to Service A on behalf ofthe user. When the parent signs in, server 170 operating in accordancewith embodiments of the invention presents the parent with a consent UIfor the minor, which displays a list of profile attributes stored in theuser profile of the user as well as profile attributes entered by theuser before the parent is rendered the consent UI. Further to theexample, the parent reviews the consent UI and determines that he or shedoes not want Service A to have the user's real postal code. The parentselects an edit profile option and submits the request. The server 170asks the parent to sign in again. After confirming that the parent is anadult (e.g., by confirming that the parent has a credit card), server170 presents the parent with an edit profile UI displaying the user'sstored profile attributes. The parent can change the postal code orother information for Service A and may save the changes to the userprofile. After the changes are saved, the parent is directed back to theconsent UI to finish granting or denying consent for the user. In oneembodiment, the consent UI may display warnings that by using Service A,the user may enter additional personal information in public forums suchas chat rooms, which may display the personal information to otherusers. If the parent still grants consent to Service A, server 170directs the parent back to Service A where the user can sign in andaccess Service A.

Back to 502, if server 170 determines that Service A wishes to complywith the comprehensive parental consent requirements, it is determinedat 510 if the birth date and country of the user are stored in the userprofile. If the birth date and country of the user are not in the userprofile, server 170 at 512 determines if the country of the user isknown but not equal-to US or Korea, which both have enacted children'sprivacy laws (e.g., COPPA of US and The Promotion of the Utilization ofInformation and Communication Network and Protection of Information Actof Korea). If this is not true, server 170 at 514 determines if the ageof the user is known and greater than fourteen. If the age of the useris either not known or not greater than fourteen, then server 170provides an accrual UI at 516 to accrue the birth date and countryinformation from the user. Upon entry of the birth date and countryinformation and selection of an option to continue the consent processat 518, server 170 proceeds to 520 to update the user profile with thenew country and birth date information. After the user profile isupdated, server 170 continues to 504 to determine if the user is a minorin order to decide which consent process (i.e., either the normalconsent process or the parent granting minor consent process) is to berendered to the user. Also illustrated in FIG. 5, server 170 alsoproceeds to 504 to determine the consent process to be rendered if (a)the birth date and country of the user are stored in the user profile;(b) the country of the user is known and not equal to US or Korea; or(c) the age of the user is known and greater than fourteen.

The accrual UI to accrue the birth date and country information alsoincludes an option for the user to cancel the consent process. If thisoption is selected at 522, then server 170 at 524 determines if ServiceA is a legacy mode service. If Service A is a legacy mode service,server 170 at 526 redirects the user back to Service A without anauthentication ticket and profile cookie. If Service A is not a legacymode service, server 170 at 528 delivers an HTTP POST to Service A with“cancel” in the body of the POST.

FIG. 6 illustrates an exemplary operational flow for reviewing and/orrevoking granted consent according to one embodiment of the invention.According to one embodiment of the invention, the user may access amember services page (e.g., a web page) hosted by server 170 allowingthe user to review and/or revoke consent previously granted to aparticular service or policy group. Upon access of the member servicespage, the user may at 602 indicate if the user intends to review and/orrevoke consent for a managed minor user. If the user indicates that heor she wishes to review and/or revoke consent for the managed minoruser, server 170 directs the user to a review consent for minor processat 604. This process allows the user to review the consent granted foror by the managed minor user and to revoke granted consent so that themanaged minor user may not be able to access the revoked service.

If the user does not indicate that he or she wishes to review and/orrevoke consent for a managed minor user, server 170 at 506 provides areview consent UI to the user via a browser. The review consent UIdisplays a list of policy groups and sites/services (including a link tothe sites/services) to which the user has granted consent and includesan option for the user to view attributes consented (includingsite-specific attributes) for a particular policy group or site/service.Upon selection of the option at 608, the user at 610 is directed to anattributes UI that shows the attributes consented and the intentions andretentions associated therewith. The attributes UI has a user-selectableoption for the user to view the privacy policy associated with theparticular policy group. Upon selection of the option at 612, server 170at 614 provides a web page displaying the privacy policy of theparticular policy group. The web page includes an option to bring theuser back to the review consent UI, as indicated at 620.

Since site-specific attributes are not stored in the user profile, theattributes UI does not display the values of such site-specificattributes. Nevertheless, the attributes UI includes an option for theuser to view the values of the site-specific attributes accrued by aparticular service. Upon selection of the option at 616, the user isprovided a web page hosted by the particular service, which displays thevalues of the site-specific attributes previously accrued by theservice. As shown in FIG. 6, both the attributes UI and the external webpage hosted by the service may include a user-selectable option for theuser to return to the review consent UI.

According to one embodiment of the invention, the review consent UIfurther has a revoke consent option for the user to revoke consentgranted to a particular policy group or site/service. Upon selection ofthe option at 622, server 170 provides a confirmation UI at 624 toexplain consequences of consent revocation (e.g., that the user can nolonger access the service). The confirmation UI has an option 626 tocancel the option to revoke. Upon selection of the “cancel” option at626, the user is directed back to the review consent UI. If the userselects a “continue” option at 628, server 170 at 630 may remove aconsent record, which indicates that the particular service has beengranted consent to access the profile attributes and site-specificattributes, from database 172. After the consent record is removed, theuser is then directed back to the review consent UI, which includes a“back” option to bring the user back to the member services page, asindicated at 632.

According to one embodiment of the invention, revoking consent to aservice also means revoking consent to members of the policy group towhich the service belongs. So after consent is revoked, other members ofthe same policy group may no longer access profile attributes stored inthe user profile. According to another embodiment of the invention, theuser may not partially revoke consent. That is, the user may not revokeconsent for a subset of the set of desired attributes while stillallowing the service access to other desired attributes.

If the user wishes to continue accessing services provided by affiliateservers 166, he or she may not revoke consent for the profile attributesdesired by server 170 as part of the registration process. These profileattributes are desired for the user to maintain his or her multi-siteuser authentication account with server 170. Accordingly, if theseprofile attributes are revoked, access to the services are not allowedunless the user re-registers with server 170 and provides the desiredprofile attributes. In another embodiment of the invention, if server170 determines that the user is a minor, the option to revoke consent isnot provided in the review consent UI. This embodiment of the inventionprevents a minor user from revoking consent granted by a parent or otherresponsible person on behalf of the minor user.

APPENDIX B provides specific examples of the profile and consent accrualprocess.

FIG. 7A to 7G show exemplary user interfaces for accruing profile andconsent in accordance with embodiments of the invention. As shown inFIG. 7A, the UI in this example has a number of form fields foraccepting information from the user. The form fields for informationthat is editable during first time consent are empty and can be filledin by the user. Further, the UI of FIG. 7A, as part of a first timeconsent process, provides an indication to the user whether theinformation will be shared. In an alternative embodiment, such asillustrated in FIG. 7B, the UI presents the user with a link to an editprofile form. FIG. 7B shows a single link for selecting the edit profileoption but it is to be understood that similar links could be providedin connection with particular information presented on the page (e.g.,next to a particular field already including information). Selecting theoption of editing the user profile navigates the user to, for example, aseparate page presenting a UI for entering edits. FIG. 7C illustrates anexemplary UI that permits the user to enter edits in response to theuser selecting the edit profile link. The user can then make desiredadditions or changes via the edit profile form.

FIG. 7D illustrates an exemplary UI that provides to the user intentionsand retentions associated with the attributes desired by a service orpreviously stored in the user profile. Intentions describe how theservice (and other members within the same policy group) will use theconsented attributes. Retentions specify how long the service (and othermembers within the same policy group) intends to retain the consentedattributes. The UI illustrated in FIG. 7D also includes a link to theprivacy policy of the policy group to which the service belongs. FIG. 7Eillustrates an exemplary UI for the user to review his or her consent.As shown in FIG. 7E, the UI includes a list of policy groups that theuser has granted consent to. The UI also displays a list ofsites/services belonging to a particular policy group. The user mayselect an option in the UI to review attributes shared with a particularpolicy group as well as to revoke consent for members of the policygroup to access the attributes. FIG. 7F illustrates an exemplary UIprovided to the user when the user selects the option to revoke consent.This UI displays the policy group and the member sites/services that theuser intends to revoke consent as well as a list of attributes (andcorresponding intentions) that are to be revoked. The UI also explainsconsequences of the consent revocation. The user may confirm therevocation by selecting the “revoke” button or cancel the revocation byselecting the “cancel” button in the UI. FIG. 7G illustrates anexemplary UI for obtaining the country and birth date information fromthe user. This UI is displayed to the user when the service is a KPPservice and the country and birth date information are not stored in theuser profile.

FIG. 8 is a block diagram illustrating an exemplary computer-readablemedium according to one embodiment of the invention. As shown, thisembodiment of the invention includes a profiling component, a consentcomponent, a user interface component, a reviewing component, a revokingcomponent, and a managed-consent component. The profiling componentstores user-specific information associated with a user. The consentcomponent receives a request from one or more services provided byaffiliate servers 166 for consent to use user information associatedwith the user and determines if the user information is stored in theprofiling component. The user interface component requests the userinformation from the user if the user information is not stored in theprofiling component. The consent component is configured to receive theuser information provided by the user via the user interface componentand to allow access by affiliate servers 166 to the received userinformation. The reviewing component displays intentions and retentionsassociated with the user information requested by affiliate servers 166.The revoking component allows the user to revoke consent for the one ormore services provided by affiliate servers 166 to use the user-specificinformation stored in the profiling component. The managed-consentcomponent allows a responsible person (e.g., a parent) of the user togrant or revoke consent for the one or more services provided byaffiliate servers 166 to use the received user information.

FIG. 9 shows one example of a general purpose computing device in theform of a computer 70. In one embodiment of the invention, a computersuch as the computer 70 is suitable for use in client computer system162, central server 170, or an affiliate server 166.

In the illustrated embodiments, computer 70 has one or more processorsor processing units 72 and a system memory 74. In the illustratedembodiment, a system bus 76 couples various system components includingthe system memory 74 to the processors 72. The bus 76 represents one ormore of any of several types of bus structures, including a memory busor memory controller, a peripheral bus, an accelerated graphics port,and a processor or local bus using any of a variety of busarchitectures. By way of example, and not limitation, such architecturesinclude Industry Standard Architecture (ISA) bus, Micro ChannelArchitecture (MCA) bus, Enhanced ISA (EISA) bus, Video ElectronicsStandards Association (VESA) local bus, and Peripheral ComponentInterconnect (PCI) bus also known as Mezzanine bus.

The computer 70 typically has at least some form of computer readablemedia. Computer readable media, which include both volatile andnonvolatile media, removable and non-removable media, may be anyavailable medium that can be accessed by computer 70. By way of exampleand not limitation, computer readable media comprise computer storagemedia and communication media. Computer storage media include volatileand nonvolatile, removable and non-removable media implemented in anymethod or technology for storage of information such as computerreadable instructions, data structures, program modules or other data.For example, computer storage media include RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disks (DVD)or other optical disk storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium that can be used to store the desired information and that canaccessed by computer 70. Communication media typically embody computerreadable instructions, data structures, program modules, or other datain a modulated data signal such as a carrier wave or other transportmechanism and include any information delivery media. The modulated datasignal has one or more of its characteristics set or changed in such amanner as to encode information in the signal. Wired media, such as awired network or direct-wired connection, and wireless media, such asacoustic, RF, infrared, and other wireless media, are examples ofcommunication media. Combinations of the any of the above are alsoincluded within the scope of computer readable media.

The system memory 74 includes computer storage media in the form ofremovable and/or non-removable, volatile and/or nonvolatile memory. Inthe illustrated embodiment, system memory 74 includes read only memory(ROM) 78 and random access memory (RAM) 80. A basic input/output system82 (BIOS), containing the basic routines that help to transferinformation between elements within computer 70, such as during startup,is typically stored in ROM 78. The RAM 80 typically contains data and/orprogram modules that are immediately accessible to and/or presentlybeing operated on by processing unit 72. By way of example, and notlimitation, FIG. 9 illustrates operating system 84, application programs86, other program modules 88, and program data 90.

The computer 70 may also include other removable/non-removable,volatile/nonvolatile computer storage media. For example, FIG. 9illustrates a hard disk drive 94 that reads from or writes tonon-removable, nonvolatile magnetic media. FIG. 9 also shows a magneticdisk drive 96 that reads from or writes to a removable, nonvolatilemagnetic disk 98, and an optical disk drive 100 that reads from orwrites to a removable, nonvolatile optical disk 102 such as a CD-ROM orother optical media. Other removable/non-removable, volatile/nonvolatilecomputer storage media that can be used in the exemplary operatingenvironment include, but are not limited to, magnetic tape cassettes,flash memory cards, digital versatile disks, digital video tape, solidstate RAM, solid state ROM, and the like. The hard disk drive 84, andmagnetic disk drive 96 and optical disk drive 100 are typicallyconnected to the system bus 76 by a non-volatile memory interface, suchas interface 106.

The drives or other mass storage devices and their associated computerstorage media discussed above and illustrated in FIG. 9, provide storageof computer readable instructions, data structures, program modules andother data for the computer 70. In FIG. 9, for example, hard disk drive94 is illustrated as storing operating system 110, application programs112, other program modules 114, and program data 116. Note that thesecomponents can either be the same as or different from operating system84, application programs 86, other program modules 88, and program data90. Operating system 110, application programs 112, other programmodules 114, and program data 116 are given different numbers here toillustrate that, at a minimum, they are different copies.

A user may enter commands and information into computer 70 through inputdevices or user interface selection devices such as a keyboard 120 and apointing device 122 (e.g., a mouse, trackball, pen, or touch pad). Otherinput devices (not shown) may include a microphone, joystick, game pad,satellite dish, scanner, or the like. These and other input devices areconnected to processing unit 72 through a user input interface 124 thatis coupled to system bus 76, but may be connected by other interface andbus structures, such as a parallel port, game port, or a universalserial bus (USB). A monitor 128 or other type of display device is alsoconnected to system bus 76 via an interface, such as a video interface130. In addition to the monitor 128, computers often include otherperipheral output devices (not shown) such as a printer and speakers,which may be connected through an output peripheral interface (notshown).

The computer 70 may operate in a networked environment using logicalconnections to one or more remote computers, such as a remote computer134. The remote computer 134 may be a personal computer, a server, arouter, a network PC, a peer device or other common network node, andtypically includes many or all of the elements described above relativeto computer 70. The logical connections depicted in FIG. 9 include alocal area network (LAN) 136 and a wide area network (WAN) 138, but mayalso include other networks. LAN 136 and/or WAN 138 can be a wirednetwork, a wireless network, a combination thereof, and so on. Suchnetworking environments are commonplace in offices, enterprise-widecomputer networks, intranets, and global computer networks (e.g., theInternet).

When used in a local area networking environment, computer 70 isconnected to the LAN 136 through a network interface or adapter 140.When used in a wide area networking environment, computer 70 typicallyincludes a modem 142 or other means for establishing communications overthe WAN 138, such as the Internet. The modem 142, which may be internalor external, is connected to system bus 76 via the user input interface134, or other appropriate mechanism. In a networked environment, programmodules depicted relative to computer 70, or portions thereof, may bestored in a remote memory storage device (not shown). By way of example,and not limitation, FIG. 9 illustrates remote application programs 144as residing on the memory device. It will be appreciated that thenetwork connections shown are exemplary and other means of establishinga communications link between the computers may be used.

Generally, the data processors of computer 70 are programmed by means ofinstructions stored at different times in the various computer-readablestorage media of the computer. Programs and operating systems aretypically distributed, for example, on floppy disks or CD-ROMs. Fromthere, they are installed or loaded into the secondary memory of acomputer. At execution, they are loaded at least partially into thecomputer's primary electronic memory. Embodiments of the inventiondescribed herein include these and other various types ofcomputer-readable storage media when such media contain instructions orprograms for implementing the steps described herein in conjunction witha microprocessor or other data processor. Embodiments of the inventionalso include the computer itself when programmed according to themethods and techniques described below.

For purposes of illustration, programs and other executable programcomponents, such as the operating system, are illustrated herein asdiscrete blocks. It is recognized, however, that such programs andcomponents reside at various times in different storage components ofthe computer, and are executed by the data processor(s) of the computer.

Although described in connection with an exemplary computing systemenvironment, including computer 70, one embodiment of the invention isoperational with numerous other general purpose or special purposecomputing system environments or configurations. The computing systemenvironment is not intended to suggest any limitation as to the scope ofuse or functionality of embodiments of the invention. Moreover, thecomputing system environment should not be interpreted as having anydependency or requirement relating to any one or combination ofcomponents illustrated in the exemplary operating environment. Examplesof well known computing systems, environments, and/or configurationsthat may be suitable for use with the embodiments of the inventioninclude, but are not limited to, personal computers, server computers,hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics including mobile phones, network PCs, minicomputers,mainframe computers, distributed computing environments that include anyof the above systems or devices, and the like.

Embodiments of the invention may be described in the general context ofcomputer-executable instructions, such as program modules, executed byone or more computers or other devices. Generally, program modulesinclude, but are not limited to, routines, programs, objects,components, and data structures that perform particular tasks orimplement particular abstract data types. Embodiments of the inventionmay also be practiced in distributed computing environments where tasksare performed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules may be located in both local and remote computer storage mediaincluding memory storage devices.

An interface in the context of a software architecture includes asoftware module, component, code portion, or other sequence ofcomputer-executable instructions. The interface includes, for example, afirst module accessing a second module to perform computing tasks onbehalf of the first module. The first and second modules include, in oneexample, application programming interfaces (APIs) such as provided byoperating systems, component object model (COM) interfaces (e.g., forpeer-to-peer application communication), and extensible markup languagemetadata interchange format (XMI) interfaces (e.g., for communicationbetween web services).

The interface may be a tightly coupled, synchronous implementation suchas in Java 2 Platform Enterprise Edition (J2EE), COM, or distributed COM(DCOM) examples. Alternatively or in addition, the interface may be aloosely coupled, asynchronous implementation such as in a web service(e.g., using the simple object access protocol). In general, theinterface includes any combination of the following characteristics:tightly coupled, loosely coupled, synchronous, and asynchronous.Further, the interface may conform to a standard protocol, a proprietaryprotocol, or any combination of standard and proprietary protocols.

The interfaces described herein may all be part of a single interface ormay be implemented as separate interfaces or any combination therein.The interfaces may execute locally or remotely to provide functionality.Further, the interfaces may include additional or less functionalitythan illustrated or described herein.

In operation, computer 70 executes computer-executable instructions suchas those described herein to manage consent between a client and anetwork server. Computer-executable instructions maintain a user profileassociated with a user of the client. Computer-executable instructionsreceive a request from a service provided by the network server for userinformation associated with the user and for consent to use therequested user information. Computer-executable instructions determineif the requested user information is included in the user profile inresponse to the request for consent. A user interface is provided to theuser via a browser of the client to collect the requested userinformation that is not included in the user profile from the user.After receiving the user information provided by the user via the userinterface, computer-executable instructions allow access by the serviceprovided by the network server to the received user information.

Information in this document, including uniform resource locator andother Internet web site references, is subject to change without notice.Unless otherwise noted, the example companies, organizations, products,domain names, e-mail addresses, logos, people, places and eventsdepicted herein are fictitious, and no association with any realcompany, organization, product, domain name, e-mail address, logo,person, place or event is intended or should be inferred.

The order of execution or performance of the methods illustrated anddescribed herein is not essential, unless otherwise specified. That is,it is contemplated by the inventors that elements of the methods may beperformed in any order, unless otherwise specified, and that the methodsmay include more or less elements than those disclosed herein.

When introducing elements of the present invention or the embodimentsthereof, the articles “a,” “an,” “the,” and “said” are intended to meanthat there are one or more of the elements. The terms “comprising,”“including,” and “having” are intended to be inclusive and mean thatthere may be additional elements other than the listed elements.

In view of the above, it will be seen that the several objects of theinvention are achieved and other advantageous results attained.

As various changes could be made in the above constructions and methodswithout departing from the scope of embodiments of the invention, it isintended that all matter contained in the above description and shown inthe accompanying drawings shall be interpreted as illustrative and notin a limiting sense.

APPENDIX A

The following illustrates exemplary SOAP-based APIs used to manipulateconsent settings. Parameter Type SemanticsEnumerateConsentRecords(UserID) UserID String PUID or email addressRETURN Array of List of policy-group IDs of existing VAL Integer consentrecords for this user QueryConsentRecord(UserID, PolicyGroupID) UserIDString PUID or email address PolicyGroupID Integer Numeric identifierfor policy group RETURN String Blob encoding the consent records for VAL(XML) that policy group. (Intentions and retention for a particularprofile attribute collected) WriteConsentRecord(UserID, PolicyGroupID,NewRecord) UserID String PUID or email address PolicyGroupID IntegerNumeric identifier for policy group NewRecord String (well- Blobencoding new consent record formed XML) RETURN Integer Success orerror-code VAL GetPolicyGroupBySiteID(SiteID) SiteID Integer Numericidentifier for the partner website RETURN Integer Policy ID VALEnumerateSites(PolicyGroupID) PolicyGroupID Integer Numeric identifierfor policy group RETURN Array of Numeric IDs for relying sites that areVAL Integer included in the given policy group

APPENDIX B

Granting Consent to Share Existing Profile Attributes

Ichiro has an EASI created at Website A. His profile includes his emailaddress, country, state, and zip. Ichiro goes to Website B for the firsttime and presses the sign-in button. Website B desires users to providecountry, state, and zip. After entering his username/password (ifnecessary) he is presented with a consent page. The consent pagedisplays Ichiro's country, state, and zip, along with a summary of howWebsite B intends to use Ichiro's data. Ichiro agrees to consent bychoosing the continue button. Website B gets Ichiro's country, state,and zip.

Site Asks for Same Profile Attributes

Ichiro has previously granted consent to Website B for country, state,and zip. He is currently logged into a website supporting a singlesign-in service. He now goes to Website C for the first time. Website Cdesires the same profile attributes as Website B (country, state, andzip). He presses the sign-in button on Website C. He is automaticallysigned in to Website C, and Website C gets country, state, and zip. Noconsent UI is displayed because he had previously granted consent toWebsite B (for the same data, same intentions, and same retention), andbecause Website B and Website C are in the same policy group.

Site Asks for Different/More Profile Attributes

Ichiro is signed in to a website hosting a single sign-in service. Hegoes to Website D for the first time. Website D is in the same policygroup to which Website B and Website C belong. Website D desires emailaddress, country, state, and zip. Ichiro presses the sign-in button onWebsite D. Ichiro sees a consent page asking for consent for emailaddress, country, state, and zip (because he has not yet granted consentto email address). He presses continue and is signed in to Website D,and Website D gets the email address, country, state, and zip.

Changing Profile Attributes during Consent

Ichiro moves from Redmond to Woodinville. Shortly after moving, he goesto Website E—a site he has never visited before. Website E wants email,country, state, and zip from its users. Ichiro presses the sign-Inbutton and is presented with a consent page with email, country, state,and zip displayed in read-only mode. He sees that his zip is still theRedmond zip of 98052. He wants to change this to the Woodinville zipcode, thus he clicks a link on the page that takes him to a pagedisplaying his full user profile. Ichiro changes his zip code to 98072and presses the “save” button. He is then taken back to the consent pageand sees the updated zip code displayed in a read-only field. He pressescontinue, is signed in to Website E, and Website E gets his zip andemail address.

Adding Missing Profile Attributes during Consent

Ichiro now goes to Website F, a site he has never been to before.Website F wants email, zip, country, gender, and birth date from itsusers. Ichiro presses the sign-in button and after entering hisusername/password (if necessary) he sees the consent page. The consentpage displays email, zip, and country in read-only mode, and gender andbirth date are shown. But since the gender and birth date profileattributes do not yet have values, they are shown as unspecified and areeditable. Ichiro selects male for gender and enters his birth datedirectly on the consent page (he doesn't have to go to the edit profilepage to do this). He presses continue, is signed in to Website F, andemail, zip, country, gender, and birth date are sent to Website F. Thenew data he entered is also saved into his user profile, and a consentrecord is written to allow Website F to request the same informationwithout UI in the future.

Canceling the Consent Process

Ichiro goes to Website G for the first time and presses the sign-inbutton. He sees the consent page. It includes birth date, and Ichirodoes not want to provide that to Website G. So he clicks the cancelbutton on the consent page and is sent back to the return URL of WebsiteG. No profile data is sent to Website G. If the site is operating inlegacy mode, Ichiro is not signed in.

Site-Specific Profile Attributes

Joe purchases a mobile phone with Internet connectivity. Joe starts hisbrowser on his phone to sign up for Website A. Due to the difficulty intyping on a phone, the registration process asks Joe to specify ausername and password. No other profile information is desired. A weeklater, Joe goes to Website A on his personal computer for the first timeand signs in. Immediately after signing in, Joe is presented with aconsent/accrual page for the standard Website A profile attributes,including member directory and white pages checkboxes, which aresite-specific attributes that are not stored in the user profile. Joeenters these and signs in to Website A. Joe then signs out. A weeklater, he goes to Website A on his personal computer and signs in. Hegets in without another consent/accrual UI.

Material Change to Site's Privacy Policy

The policy group to which Website A belongs makes a material change toits privacy policy. It will now sell the user's profile information tothird parties. Joe now goes to Website A, a site that he has usedbefore. He is asked to consent to share his data again with the newintentions.

A Child Signs in to a KPP Site

Abby's son, Tanner, signs in to Website D for the first time to use hissoccer team community site. Tanner has a user profile that includes hisemail address. Since Website D complies with the COPPA regulation,Tanner is shown a consent page that asks him to provide his birth dateand country, as well as gender which Website D wants for targetedadvertising. Tanner enters these values into the consent/accrual UI andpresses continue. Since Tanner is a child and his parent has not yetprovided consent to Website D, the next page he sees asks if his parentis with him to provide consent. He indicates “Yes” because his parent ispresent. Abby logs in, enters her credit card to prove she is an adult,reads the intentions, grants consent to Website D, and then sees thesame profile consent/accrual page again with the data that Tannerentered in the initial profile consent/accrual page (except forsite-specific attributes, the values of which are not stored in the userprofile). This page also explains to Abby that Website D might allowTanner to enter additional information in public forums such as chatrooms that may display the information to other users. Abby thinks thisis fine and presses the continue button. She is logged out andredirected back to Website D where Tanner signs in and gets access tohis soccer team community site.

A week later, Tanner signs in to Website H, which is not a KPP site. Toaccess the site, Website H desires users to provide their occupationinformation. Instead of showing the normal profile consent page, the “Isyour parent with you page” is shown. Abby is present. Accordingly, shepresses “Yes” and signs in. She sees the profile consent page asking foroccupation, selects “Student,” and presses continue. She is signed outand redirected back to Website H where Tanner can now sign in. A weeklater, Tanner starts getting junk email at his email account. Abbybelieves this is caused by Tanner sharing his profile information withWebsite D, thus she goes to Member Services and denies consent toWebsite D.

Reviewing and Revoking Consent

Ichiro decides that he no longer wants Website E to have access to hisprofile data. So he goes to the Privacy section of Member Services andviews a page showing the policy groups to which he has granted consent.Next to a particular policy group is a list of the attributes to whichhe has granted consent. He sees Website E, checks the box next to it,presses the “revoke” button, reviews the confirmation page explainingthe consequences of revoking consent, and presses “continue” to completethe action.

Revoking Consent for a Child

Abby signs in to Member Services and chooses the Privacy section. Fromthe Privacy section, she chooses the Managed Accounts link and reviewsthe consent settings for her children. When she discovers that she hasgranted full consent to Website E for Tanner, she revokes consentcompletely so that Tanner will not be able to sign in to Website E inthe future.

1. A method of managing consent between a client and a network server,said client and said network server being coupled to a datacommunication network, said network server providing a service to a uservia the client, said client operating a browser configured to permit theuser to communicate on the data communication network, said methodcomprising: maintaining a user profile associated with the user;receiving a request from the service provided by the network server foruser information associated with the user and for consent to use therequested user information; determining, in response to the request forconsent, if the requested user information is included in the userprofile; providing a user interface via the browser to collect therequested user information that is not included in the user profile fromthe user; receiving the user information provided by the user via theuser interface; and allowing access by the service to the received userinformation.
 2. The method of claim 1, further comprising updating theuser profile with the received user information.
 3. The method of claim1, further comprising allowing, in response to the request for consent,access by the service to the requested user information if the userinformation is included in the user profile.
 4. The method of claim 1,wherein the user profile is being maintained by a central server, saidcentral server being coupled to the data communication network, andwherein the user interface is being provided by the central server anddisplays user information previously included in the user profile. 5.The method of claim 1, wherein the user interface displays auser-selectable option for viewing intention information associated withthe requested user information, said intention information describinghow the requested user information will be used by the service providedby the network server.
 6. The method of claim 5, further comprisingproviding an intention user interface via the browser for displaying theintention information, said intention user interface being provided inresponse to the user-selectable option being selected by the user. 7.The method of claim 6, wherein said intention user interface furtherdisplays retention information associated with the requested userinformation, said retention information specifying how long therequested user information will be retained by the service provided bythe network server.
 8. The method of claim 6, wherein the serviceprovided by the network server is a member of a policy group, andwherein said intention user interface further displays a list of membersof said policy group.
 9. The method of claim 8, wherein said intentionuser interface further displays a second user-selectable option forviewing a privacy policy associated with said policy group, said privacypolicy relating to how user information that the policy group is grantedconsent to use is to be protected.
 10. The method of claim 9, furthercomprising providing a policy user interface via the browser fordisplaying the privacy policy, said policy user interface being providedin response to the second user-selectable option being selected by theuser.
 11. The method of claim 1, wherein the service provided by thenetwork is granted consent to use user information included in the userprofile.
 12. The method of claim 11, further comprising providing arevocation user interface via the browser for allowing the user torevoke consent for the service provided by the network server to use theuser information included in the user profile, said revocation userinterface displaying a list of services for which the user has grantedconsent to use the user information included in the user profile. 13.The method of claim 12, wherein said revocation user interface furtherdisplays a user-selectable option for revoking consent for the serviceprovided by the network server to use the user information included inthe user profile.
 14. The method of claim 13, further comprisingrevoking consent for the service provided by the network server to usethe user information included in the user profile in response to theuser-selectable option being selected by the user.
 15. The method ofclaim 1, further comprising providing an administrator user interface toa responsible person of the user in response to said receiving the userinformation provided by the user, said another user interface allowingthe responsible person of the user to grant consent for the serviceprovided by the network server to use the received user information. 16.The method of claim 15, wherein said allowing access by the service tothe received user information comprises allowing access by the serviceto the received user information if consent for the service to use thereceived user information is granted by said responsible person.
 17. Themethod of claim 15, wherein said responsible person is a parent of theuser.
 18. The method of claim 1, wherein one or more computer-readablemedia have computer-executable instructions for performing the methodrecited in claim
 1. 19. An authentication system comprising: anauthentication server coupled to a data communication network; anauthentication database associated with the authentication server, saidauthentication database being configured to store authenticationinformation for comparison to login information provided by a user forauthenticating the user, said authentication database further beingconfigured to store user-specific information identifying the user withrespect to one or more services provided by at least one affiliateserver coupled to the data communication network, said affiliate serverbeing configured to provide the one or more services to the user via aclient coupled to the data communication network; said authenticationserver being configured to receive a request from the user for a serviceto be provided by the affiliate server, said authentication serverfurther being configured to authenticate the user responsive to therequest when login information retrieved from the user via the datacommunication network matches the authentication information stored inthe authentication database; said authentication server being furtherconfigured to maintain a user profile storing the user-specificinformation, to receive a request from the requested service for userinformation associated with the user and consent to use the requesteduser information, to determine if the requested user information isstored in the user profile in response to the request for consent; andsaid authentication server being further configured to provide a userinterface to collect the requested user information that is not storedin the user profile from the user, to receive the user informationprovided by the user via the user interface in response, and to allowaccess by the requested service to the received user information. 20.The system of claim 19, wherein the authentication server is configuredto update the user profile with the received user information.
 21. Thesystem of claim 19, wherein the authentication server is configured toallow, in response to the request for consent, access by the requestedservice to the requested user information if the user information isstored in the user profile.
 22. The system of claim 19, wherein the userinterface provided by the authentication server displays theuser-specific information previously stored in the user profile.
 23. Thesystem of claim 19, wherein the user interface provided by theauthentication server displays a user-selectable option for viewingintention information associated with the requested user information,said intention information describing how the requested user informationwill be used by the requested service.
 24. The system of claim 23,wherein the authentication server is configured to provide an intentionuser interface for displaying the intention information, said intentionuser interface being provided by the authentication server in responseto the user-selectable option being selected by the user.
 25. The systemof claim 24, wherein said intention user interface further displaysretention information associated with the requested user information,said retention information specifying how long the requested userinformation will be retained by the requested service.
 26. The system ofclaim 24, wherein the requested service is a member of a policy group,and wherein said intention user interface further displays a list ofmembers of said policy group.
 27. The system of claim 1, wherein therequested service is granted consent to use the user-specificinformation stored in the user profile.
 28. The system of claim 27,wherein the authentication server is configured to provide a revocationuser interface for allowing the user to revoke consent for the requestedservice to use the user-specific information stored in the user profile,said revocation user interface displaying a list of services that theuser has granted consent to use the user-specific information stored inthe user profile.
 29. The system of claim 28, wherein said revocationuser interface further displays a user-selectable option for revokingconsent for the requested service to use the user-specific informationstored in the user profile.
 30. The system of claim 29, wherein theauthentication server is configured to revoke consent for the requestedservice to use the user-specific information stored in the user profilein response to the use-selectable option being selected by the user. 31.The system of claim 19, wherein the authentication server is configuredto provide an administrator user interface to a responsible person ofthe user in response to the received user information, saidadministrator user interface allowing the responsible person of the userto grant consent for the requested service to use the received userinformation.
 32. The system of claim 31, wherein the authenticationserver is configured to allow access by the requested service to thereceived user information if consent for the requested service to usethe received user information is granted by said responsible person. 33.One or more computer-readable media having computer-executablecomponents for managing consent between a client and at least onenetwork server, said client and said network server being coupled to adata communication network, said network server providing a service to auser via the client, said computer-readable media comprising: aprofiling component for storing user-specific information associatedwith the user; a consent component for receiving a request from theservice provided by the network server for user information associatedwith the user and for consent to use the requested user information,said consent component further determining if the requested userinformation is stored in the profiling component in response to therequest for consent; a user interface component for collecting therequested user information that is not included in the profilingcomponent from the user; and wherein the consent component is configuredto receive the requested user information provided by the user via theuser interface component and to allow access by the service to thereceived user information.
 34. The computer-readable media of claim 33,wherein the consent component is configured to store the received userinformation in the profiling component.
 35. The computer-readable mediaof claim 33, wherein the user interface component is configured todisplay the user-specific information previously stored in the profilingcomponent.
 36. The computer-readable media of claim 33, furthercomprising a reviewing component for displaying intention informationassociated with the user information, said intention informationdescribing how the user information will be used by the service providedby the network server.
 37. The computer-readable media of claim 36,wherein the reviewing component is configured to display retentioninformation associated with the user information, said retentioninformation specifying how long the user information will be retained bythe service provided by the network server.
 38. The computer-readablemedia of claim 36, wherein the service provided by the network server isa member of a policy group, and wherein the reviewing component isconfigured to display a list of members of said policy group.
 39. Thecomputer-readable media of claim 33, further comprising a revokingcomponent for allowing the user to revoke consent for the serviceprovided by the network server to use the user-specific informationstored in the profiling component, said revoking component displaying alist of services that the user has granted consent to use theuser-specific information stored in the profiling component.
 40. Thecomputer-readable media of claim 33, further comprising amanaged-consent component for providing the received user information toa responsible person of the user to allow the responsible person of theuser to grant consent for the service provided by the network server touse the received user information.